CVE-2008-0976

CVE-2008-0976 affects Double-Take 5.0.0.2865 and earlier (distributed under HP StorageWorks Storage Mirroring and other names). The underlying issue is a NULL pointer dereference in a network daemon exploitable by malformed packets, with demonstrated packet types 0x2722 and 0x272a, leading to rem...

CVE-2008-0973

The CVE-2008-0973 entry describes a buffer overflow in Double-Take (HP StorageWorks Storage Mirroring) version 4.5.0.1629 and other 4.5.0.x releases. The vulnerability is exploitable by remote attackers via a packet containing a long string in the username field. The impact is listed as unknown/u...

CVE-2008-0979

CVE-2008-0979 concerns a stack consumption vulnerability in Double-Take 5.0.0.2865 and earlier (also under HP StorageWorks Storage Mirroring and other names). The issue allows a remote attacker to cause a denial of service (daemon crash) by sending a certain packet that triggers recursive calling...

CVE-2008-0974

CVE-2008-0974 affects Double-Take 5.0.0.2865 and earlier (also distributed under HP StorageWorks Storage Mirroring). The vulnerability allows remote attackers to cause a denial of service (daemon termination) via either: (1) a large vector value triggering a “vector too long” exception, or (2) a ...

CVE-2008-0977

CVE-2008-0977 affects Double-Take 5.0.0.2865 and earlier (HP StorageWorks Storage Mirroring family). A long network packet can trigger an allocation of a large amount of memory, allowing remote attackers to cause a denial of service by crashing the daemon. No remediation or exploitation details a...

CVE-2008-0978

CVE-2008-0978 affects Double-Take 5.0.0.2865 and earlier (HP StorageWorks Storage Mirroring name and other names). A remote attacker can obtain sensitive information by sending a crafted packet of type 0x2728 (OS/path info), 0x274e (Ethernet adapters), 0x2726 (filesystem info), 0x274f (printer dr...

CVE-2008-0975

CVE-2008-0975 affects Double-Take (HP StorageWorks Storage Mirroring lineage) up to version 5.0.0.2865, where a remote attacker can cause CPU exhaustion by sending a -1 value in the vector size field. Core details indicate the issue is a remote DoS via malformed vector size; no remediation or exp...